Perhaps adding a post-messages entry could encourage clients to update their dependencies? 🤔

There is not a lot of users of this library, so next version those deprecated package will be removed. Dune perhaps already warn that they are deprecated.

Platform-wise it looks like conf-flint on Alpine, Centos, and FreeBSD could use a hand

Normally alpine should be fixed. On the other hand the package doesn't exists anymore in centos, and doesn't exists in freebsd. I don't want to forbid to install the package on this distribution since a user can install the C library manually. Perhaps there is some ci-dont-test: {os = freebsd}?

For the segfault on arm32 and ppc, I'm in the process of changing the way the binding is written. So it could disappear then. Should I do something for those platform in the mean time?

There is not a lot of users of this library, so next version those deprecated package will be removed. [,,,]

OK, thanks for sharing!

Platform-wise it looks like conf-flint on Alpine, Centos, and FreeBSD could use a hand

Normally alpine should be fixed. On the other hand the package doesn't exists anymore in centos, and doesn't exists in freebsd. I don't want to forbid to install the package on this distribution since a user can install the C library manually.

Good point!

Perhaps there is some ci-dont-test: {os = freebsd}?

We cannot prevent the CI run but we can silence the CI-error on FreeBSD: 🤷

x-ci-accept-failures: ["freebsd-14.3"]

For the segfault on arm32 and ppc, I'm in the process of changing the way the binding is written. So it could disappear then. Should I do something for those platform in the mean time?

If the packages work reasonably on arm32 and ppc64 except for test suite corner cases, we could just disable runtest on those platforms:

    "@runtest" {with-test & arch != "arm32" & arch != "ppc64"}

Alternatively, we could just disable the packages entirely on the platforms to prevent potential users from chasing segfault ghosts: 👻

available: arch != "arm32" & arch != "ppc64"